User Story Mapping
1. Station
USER PROFILES
- Station Node Operator: Individual (or group) that downloads station modules and runs on their machine, serving jobs to the broader network for a fee.
- Assumed to be less technical / sophisticated than a full mining operator
- Cares about getting paid, security (don’t want anything malicious running on computer) and seeing the results of their work
- Module Builder: Utilizes the Station system and builds a bespoke application (or selects from template) to deploy modules to the network of lightweight nodes
- Developer in a broader organization
- Cares about access to pre-existing sets of trusted nodes that can be paid / incentivized to perform decentralized work, a strong set of documents and strong DX. Concerns on safety and ease of use / ongoing maintenance of a module
- Module Funder: Runs an organization / entity that would like to incentivize
- Business, Product or Protocol leader making capital allocation decisions
- Cares about fraudulent usage of funds, tracking outcomes generated from their investment, cash flow required to operate
| User: | 1. Station Node Operator | 2. Module Builder | 3. Module funder |
|---|---|---|---|
| Motivations | a. I want to earn some extra FIL by downloading the Station app to my personal computer to run it idly in the background b. I believe in the ethos of decentralization and want to contribute my machine to the cause | a. I am looking for a deployment target that’s a distributed network of machines capable of performing proofs or checks for my network. | I’m looking to incentivize work in a decentralized system to reach my business goals |
| Example profile | Web3 developer | Compute over Data, Saturn | Protocol Labs (FIL+, ReputationDAO), WitnessChain, etc. |
| Acquisition path | - Marketing through PLN slack - PLN / Filecoin Newsletter - Twitter advertising | - Direct outreach - Developer documentation | - Direct Outreach - Thought leadership? |
| Key Activity | Setup Station desktop app | Build and deploy a module on station | Funding existing or new Station modules |
| Actions 👇🏽 | Navigate to filstation.app | Navigate to Module Builder docs | Identify incentive opportunity available through station |
| Download the app to personal computer | Design and build (or select template) for a module | Identify path to design/deploy a module | |
| Agree to terms and conditions | Deploy module | Fill contract Balance | |
| Begin performing jobs | Marketing to download Station and run module/nodes | Monitor ROI and fraud | |
| See earned FIL and transfer if desired | Fill contract balance for incentives |
USER STORIES - Functionality required for Lab Week
- [Node Operator] As a Node Operator, I want to download station app to my desktop computer and run it idly in the background to earn extra FIL
- [Node Operator] As a Node Operator, I want to be able to view my daily rewards / activity in a digestible interface so I can assess whether it is valuable to continue
- [Node Operator] As a Node Operator, I want to be able to withdraw my accumulated FIL from my Station wallet every 2 weeks
- [Module Builder] As a Module Builder, I want to utilize a pre-existing set of smart contracts that can be composable with my own provided services
- [Module Builder] As a Module Builder, I want access to a testnet where I can deploy new modules and troubleshoot before mainnet launch
- [Module Funder] As a Module Funder, I would like to have clear, easy instructions or paths to build and fund a new module.
- [Module Funder] As a Module Funder, I would like to see the activities / outcomes generated from my provided funding in a report
- [Module Funder] As a Module Funder, I want to understand the level of expected fraudulent activity from my investment in a report
- [Module Funder] As a Module Funder, I want a smooth integration between my deployed Station module and a production wallet I use to fund the contract every 2 weeks
2. Meridian
USER PROFILES
- Meridian (non-Station) Implementer: Developer that wants to fork Meridian contracts and use for a new use case
- Developer (individual or in an org) that wants to use Meridian contracts for bespoke use cases
- Cares about clear Meridian documentation
- Meridian PaaS User: Developer that wants to deploy code to a complete development and deployment environment with Meridian contracts running in the background
- Developer (individual or in an org) that wants to use Meridian payment rails for non-Station application
- Cares about a clean DX for deploying to a platform (vs. utilizing raw contracts), and would like to do so permissionlessly and without needing to modify existing scripts
| User: | 1. Meridian (non-Station) Implementer | Meridian PaaS Customer |
|---|---|---|
| Motivations | I want to fork the Meridian Contracts with a clear set of examples to create my own implementation | I want to deploy to a platform (not use the raw contracts) permissionlessly and w/o modifying scripts |
| Example profile | Creator of a DeFi incentive system that wants to use the Meridian contracts/services to save time | Dev wants to reward quantifiable behavior by deploying code directly in a platform (not using raw contracts) |
| Acquisition path | - Marketing to developer communication channels | - Social media, newsletters, outreach, case studies |
| Key Activity | Fork Meridian | Input xyz into abc |
| Actions 👇🏽 | Reads Meridian Docs | Opens Meridian platform appapp |
| Forks GitHub Repo | Configures |
USER STORIES
- [Meridian Implementer] As a (non-Station) Meridian Implementer, I want to learn about use cases for the Impact Evaluator Meridian contract
- [Meridian PaaS User] As a Meridian PaaS user, I want to
-
Spark
USER PROFILES
- Spark Beneficiary: Individual or group who benefit from the data output by Spark modules that is relevant to aspects of the Filecoin ecosystem (e.g. Reputation WG)
- PLN incentive initiative that wants a decentralized method for checking the quality of storage provided by SPs
- Cares about having an easy interface with which to connect project with SPARK (and clean DX to do so), and cares about
- Spark Funder: Beyond PL’s initial sponsorship, this is the individual or group who’s resources funding the Station node payouts in return for a desired service
- See
| User: | Beneficiary | Funder |
|---|---|---|
| Motivations | Beneficiary | Funder |
| Example profile | FIL+ admins, Reputation DAO, and others who benefit from quantitative data on retrievability | Protocol Labs or Filecoin Protocol |
| Acquisition path | - Direct conversations with key stakeholders across the PLN | - Direct conversations or BD - Eventually a FIP? |
| Key Activity | Use SPARK as a datasource | Sending funds to IE contract |
| Actions 👇🏽 | I navigate to docs for SPARK interface | |
| [wip] I set up SPARK as a datasource |
USER STORIES
- [SPARK Beneficiary] As a FIL+ program manager, I want to be able to use SPARK as a datasource for moving eligibility checks for the FIL+ program from qualitative to quantitative
- [SPARK Beneficiary] As a Reputation DAO member, I want to use SPARK as a datasource, with which I can further monetize the value of the DataDAO
- [SPARK Beneficiary] As a SP, I want to be able to reproduce SPARK results and to not have any un-rewarded requests for my time, attention, or resources